Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

[CSP] Federation Self-Service Flow Process & Overview (76201)

Last Updated: 4/21/2022Categories: How toTotal Views: 14702Language:
English

6 like this article

Subscribe to get an email
newsletter with new updates

6 people found this helpful Please provide article feedback:

Purpose

This KB Article is geared towards federation setup to access VMware Cloud Services and not for EUC WS1 Access On-prem or EUC WS1 Access SaaS customers.

Every large enterprise would like to use their own identity and MFA (Multi-factor Authentication) with VMware Cloud Services. Up until now, customers were required for their users to create and use their VMware ID to authenticate. Enterprise Federation feature enables customers to bring their corporate identities and credentials to log in to VMware Cloud Services and link their VMware ID accounts.  In addition to federation, they can manage bulk access to their services, by using their enterprise groups in Cloud Services Platform (CSP) Identity & Access Management (IAM).  This feature is only available for customers who have an active subscription in the VMware CSP for any SaaS Products.

Resolution

Enterprise Federation cannot be set on per-user or Organization (Org) basis and is not feature flag based. Enterprise Federation setup is per domain. Using ACME as an example, when federation is setup for the ACME domain, all the users from ACME.com will be required to authenticate against the corporate identity solution and not Customer Connect. The following checklist has been created to help customers understand the steps and their role. Please be aware that this entire process can take anywhere from 1-3 weeks to complete depending on the complexity of the Directory setup.

Prerequisites

Roles

The Organization Owner is responsible for initiating the self-service workflow on behalf of the organization and inviting an Enterprise Administrator to complete the setup. Note: Organization Owners who hold system administrator roles with their enterprise and have sufficient knowledge of the enterprise directory service and identity provider configuration, can act as enterprise administrators for the federation setup.

For details on how the Organization Owner can begin the self-service federation workflow from the Cloud Services Platform (CSP), please view page 5 of our Setting Up Enterprise Federation with VMware Cloud Services Guide.

The Enterprise Administrator is a system administrator who belongs to the central security team for your enterprise and manages the directory services and identity providers.

It is the responsibility of the Enterprise Administrator to determine the type of federation setup that is best suited to your enterprise: Dynamic (connectorless) authentication setup or Connector-based authentication setup. Please note how the two options vary below:

Federation setup

Authentication method

User and group provisioning

Dynamic (connectorless) authentication setup

SAML 2.0 Identity Provider

Dynamic provisioning: SAML JIT

Connector-based authentication setup

SAML 2.0 Identity Provider OR Workspace ONE Access connector authentication methods

Pre-provisioning: syncing users and groups from your Active Directory

Note: The designated Enterprise Administrator can invite other administrators to help with the setup.

Prerequisites for Dynamic (Connectorless) Authentication Setup

Verify that you can access your identity provider console and IDP metadata URL.

Prerequisites for Workspace ONE Access Connector Setup

Verify that you can access and modify the federated domains' DNS records for domain verification.

Verify that your host machine is with installed MS Windows Server 2012 R2 or later, and that you can access your enterprise directory.

The host Windows machine must have a static IP address and a DNS resolvable FQDN.

The connector must have network access to Active Directory on ports 389/636.

Verify that your corporate firewall is configured to make an outbound connection from the Workspace ONE Access connector to Port 443 for interaction with the hosted tenant service.

If you want to add domains to the allow list, you must add the *.workspaceoneaccess.com (Workspace ONE Access Production Tenant URL) domains to your list of allowed domains.

The host Windows server machine or virtual machine can be deployed on-premises, on a VMware Cloud on AWS, or can be an Elastic Compute Cloud instance. The host on which Workspace ONE Access connector is installed must be able to access your enterprise directory over LDAP/LDAPS.

For additional information about installing the Workspace ONE Access connector, review the overall Workspace ONE Access Connector 20.01 Systems Requirements.

Verify that you have a user or service account with read permissions on Active Directory and a nonexpiring password for AD Bind User DN/Name to sync groups and users. The service account must have the following attributes: firstname, lastname, displayname, and email address. The email address for the service account can be a dummy value.

Note: If you use a service account with an expiring password policy and if a password expires before renewal, groups and users cannot be synced unless you reestablish the connection between Active Directory and the Workspace ONE Access connector.

The required attributes to sync users for access to VMware Cloud services are first name, last Setting Up Enterprise Federation with VMware Cloud Services Guide VMware, Inc. 12 name, email address, user name, and domain. If your enterprise uses User Principal Name (UPN) for authentication, it must be available as a user profile attribute.

Important: User passwords are never synced.

Procedure

While an overview is provided here, our Setting Up Enterprise Federation with VMware Cloud Services Guide provides additional information on the multiple procedures involved in establishing enterprise federation. Please navigate to the relevant page within this resource for the following processes:

Steps for Dynamic (connectorless) Federation setup: page 20

Verify domain

Configure the identity provider

Complete setup

Link your VMware ID account

Steps for Connector-based Federation setup: page 28

Verify domains

Install Workspace ONE Access Connector

Sync groups and users

Configure the identity provider

Complete setup

Link your VMware ID account

Troubleshooting Federation: page 42

 Get Support

Modifications to the Federation Setup: page 45

Make changes to synced groups and users

Make changes to Directory settings

Add new domains for Enterprise Federation

Identity Governance and Administration: page 51

 Enable advanced identity and Governance Administration features for federated domains

Frequently Asked Questions (FAQs)

Please review page 14 of our Setting Up Enterprise Federation with VMware Cloud Services Guide for a detailed list of frequently asked questions and answers.

Related Information

Supported MFA Applications

Setting Up Federated Identity Management for VMC on AWS – Authentication with Okta IdP

AD FS Integration

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
Downloading and Installing the standalone VMware Remote Console (VMRC) in vSphere (2091284)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Workspace ONE Access

VMware Workspace ONE

VMware Identity Manager

VMware Cloud on AWS

Related Versions:

Take Our Survey

Support Assistant